home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9611 / 000059_owner-urn-ietf _Wed Nov 6 10:00:52 1996.msg < prev    next >
Internet Message Format  |  1997-02-19  |  2KB
  1. Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id KAA11713 for urn-ietf-out; Wed, 6 Nov 1996 10:00:52 -0500
  2. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id KAA11708 for <urn-ietf@services.bunyip.com>; Wed, 6 Nov 1996 10:00:50 -0500
  3. From: Harald.T.Alvestrand@uninett.no
  4. Received: from domen.uninett.no by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
  5.         id AA10059  (mail destined for urn-ietf@services.bunyip.com); Wed, 6 Nov 96 10:00:48 -0500
  6. Received: from domen.uninett.no by domen.uninett.no with SMTP (PP) 
  7.           id <07869-0@domen.uninett.no>; Wed, 6 Nov 1996 15:58:16 +0100
  8. X-Mailer: exmh version 1.6.7 5/3/96
  9. To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
  10. Cc: Fisher Mark <FisherM@is3.indy.tce.com>,
  11.         "urn-ietf@bunyip.com" <urn-ietf@bunyip.com>
  12. Subject: Re: [URN] Persistence as part of URN framework
  13. In-Reply-To: Your message of "Wed, 06 Nov 1996 14:31:36 GMT." <2.2.32.19961106143136.006e2924@sherekhan.jungle.bt.co.uk>
  14. Mime-Version: 1.0
  15. Content-Type: text/plain; charset=us-ascii
  16. Date: Wed, 06 Nov 1996 15:58:12 +0100
  17. Message-Id: <7866.847292292@domen.uninett.no>
  18. Sender: owner-urn-ietf@services.bunyip.com
  19. Precedence: bulk
  20. Reply-To: Harald.T.Alvestrand@uninett.no
  21. Errors-To: owner-urn-ietf@bunyip.com
  22.  
  23. rbriscoe@jungle.bt.co.uk said:
  24. > A URN user is not just someone who clicks on one. It could also be 
  25. > someone who publishes one (that you have published) to refer to your 
  26. > work in their work. They need to know how long they should reliably 
  27. > use your URN. Meta-data that any party might need is a proper 
  28. > candidate for holding in infrastructure. 
  29.  
  30. That's what I called an "URN buyer"
  31. When I get an URN from someone, and apply it to my resources,
  32. I would figure that I "own" that URN.
  33.  
  34. rbriscoe@jungle.bt.co.uk said:
  35. > Get my drift?
  36. No. I still think the information publisher ("URN buyer) is the one
  37. for which this information is vital, and that the information should
  38. be part of the business contract between the provider of the URN
  39. namespace and the information publisher.
  40. The URN user (the one who looks up the information) should have no
  41. need to know or care.
  42.  
  43.  
  44.                                Harald A
  45.  
  46.  
  47.  
  48.